約 5,857,766 件
https://w.atwiki.jp/keisks/pages/443.html
Maven+Eclipseで確認。 pom.xmlに追加する（https //logging.apache.org/log4j/2.x/maven-artifacts.html） log4j2.xmlをsrc/java/resource/に配置する。基本的な設定としては ?xml version="1.0" encoding="UTF-8"? configuration status="OFF" Appenders Console name="Console" target="SYSTEM_ERR" // あるいはSYSTEM_OUT PatternLayout pattern="%d{DEFAULT} | [%t] | %-5level | %c{36} | %msg%n"/ /Console File name="File" fileName="logs/nlp4j.log" // 出力先 PatternLayout pattern="%d{yyyy-MM-dd HH mm ss.SSS} | [%t] | %-5level | %c{36} | %msg%n"/ /File /Appenders Loggers Root level="error" // デフォルトの設定 AppenderRef ref="Console"/ // どこに出すか /Root Logger name="com.keisks.nlp4j" level="trace" additivity="false" // パッケージごとの追加設定（上書きされる） AppenderRef ref="Console"/ AppenderRef ref="File"/ // ファイルにも書きたい場合は追加する。Fileという名前は上の File name="File"で設定している /Logger /Loggers /configuration Enjoy logging by log4j2!! PatternLayoutについては http //yamashiro0110.hatenadiary.jp/entry/2014/08/24/093336
https://w.atwiki.jp/mekagazira/pages/15.html
javacでのサーブレットのコンパイル Antでのコンパイル javaでAPIを作成する メモ javacでのサーブレットのコンパイル c \Tomcat6_0_16\webapps\anttest javac -d WEB-INF/classes -cp .;"C \Tomcat6_0_16\lib/servlet-api.jar" src/HelloWorldServlet.java Antでのコンパイル Antのセットアップ ダウンロード http //ant.apache.org/bindownload.cgi PATHを通す ANT_HOMEを設定し、PATHに%ANT_HOME%\binを追加する。 プロジェクトルートにbuild.xmlを置く ?xml version="1.0" encoding="Shift_JIS"? project default="compile" !-- ソースファイルがあるディレクトリ -- property name="src.dir" value="src" / !-- クラスファイルを出力するディレクトリ -- property name="classes.dir" value="WEB-INF/classes" / !-- ライブラリのあるディレクトリ -- property name="lib.dir" value="../../lib" / path id="classpath" fileset dir="${lib.dir}" include name="**/*.jar" / /fileset /path !-- コンパイル -- target name="compile" mkdir dir="${classes.dir}" / javac srcdir="${src.dir}" destdir="${classes.dir}" classpathref="classpath" / /target /project ant実行 c \Tomcat6_0_16\webapps\anttest ant Buildfile c \Tomcat6_0_16\webapps\anttest\build.xml compile [javac] c \Tomcat6_0_16\webapps\anttest\build.xml 24 warning includeantruntime was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to c \Tomcat6_0_16\webapps\anttest\WEB-INF\classes BUILD SUCCESSFUL Total time 1 second javaでAPIを作成する 以下の様にjspを作成してiniの様な「名前」=「値」で値を返しえあげる。 %@ page language="java" contentType="text/plain; charset=Windows-31J" % return_code= %=request.getAttribute("return_code")% error_reason= %=request.getAttribute("error_reason")% open_date= %=request.getAttribute("open_date")% SYSTEMERROR.txt return_code=9 error_reason=Exception_occured web.xml ?xml version="1.0" encoding="ISO-8859-1"? !DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http //java.sun.com/dtd/web-app_2_3.dtd" web-app servlet servlet-name hogeServlet /servlet-name servlet-class com.mkeka.hogeServlet /servlet-class init-param param-name SQLSTR /param-name param-value SELECT * FROM hogeTable WHERE FLG = 01 AND USER_ID = ? /param-value /init-param init-param init-param param-name RESPONSE_PAGE /param-name param-value RESPONSE.jsp /param-value /init-param /servlet !-- Standard Action Servlet Mapping -- servlet-mapping servlet-name hogeServlet /servlet-name url-pattern /hogeServlet /url-pattern /servlet-mapping error-page error-code 500 /error-code location /SYSTEMERROR.txt /location /error-page error-page exception-type java.lang.Exception /exception-type location /SYSTEMERROR.txt /location /error-page /web-app メモ javax.servletとjavax.servlet.http javax.servlet･･･通信プロトコルに依存しない機能を提供するクラス・インターフェースから構成されている javax.servlet.http･･･HTTPに依存する機能を提供するクラス・インターフェースから構成されている log4j書き方 private static Log log = LogFactory.getLog(hogeServlet.class.getName()); commons-logging.jar log4j-1.2.8.jar #log4j.rootCategory=DEBUG, A1,S1,W1 log4j.rootCategory=DEBUG, A1,W1,S1 # A1 is set to be a FileAppender which outputs to File. log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender log4j.appender.A1.File=/service/log/hogeapp/app.log log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=%d{yyyy MM dd HH mm ss} [get39info %t] %-5p %l %m%n log4j.appender.W1=org.apache.log4j.DailyRollingFileAppender log4j.appender.W1.File=/service/log/hogeapp/appwarn.log log4j.appender.W1.Threshold=WARN log4j.appender.W1.layout=org.apache.log4j.PatternLayout log4j.appender.W1.layout.ConversionPattern=%d{yyyy MM dd HH mm ss} [get39info %t] %-5p %l %m%n log4j.appender.S1=org.apache.log4j.net.SyslogAppender log4j.appender.S1.SyslogHost=localhost log4j.appender.S1.Facility=user log4j.appender.S1.Threshold=ERROR log4j.appender.S1.layout=org.apache.log4j.PatternLayout log4j.appender.S1.layout.ConversionPattern=[get39info] %-5p(APL) %l %m%n javaでHelloWorld Ant編 Servlet API Documentation
https://w.atwiki.jp/myoss/pages/45.html
Tomcatのコンソール出力をLog4Jを使用してファイルに出力する方法を示す。 構成情報 Tomcat 5.5.9 JDK 1.5.0_04 Commons Logging 1.0.4 Log4J 1.2.12 設定方法 1.Commons loggingとLog4Jをダウンロードし、[$CATALINA_HOME]/common/libにコピーする。 2.以下の内容で、log4j.propertiesを、[$CATALINA_HOME]/common/classes直下に作成する。 log4j.rootLogger=debug,R log4j.appender.R=org.apache.log4j.RollingFileAppender log4j.appender.R.File=${catalina.home}/logs/tomcat.log log4j.appender.R.MaxFileSize=10MB log4j.appender.R.MaxBackupIndex=10 log4j.appender.R.layout=org.apache.log4j.PatternLayout log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n log4j.logger.org.apache.catalina=DEBUG, R 3.Tomcatを起動する。 おおぉー、今までコンソール出力されていたものが、[$CATALINA_HOME]/logs/tomcat.logに出力されてますね。 デバックモードやappenderを変えることで、実際の運用でも使用できそうですね。
https://w.atwiki.jp/duke15/pages/31.html
Tomcat project を作り、Struts support, Spring nature をつける コンパイル先が WEB-INF/classes になっていなければ、このフォルダを作り、コンパイル先に指定する。 WEB-INF/jsp を作る WEB-INF/web.xml にdescription がなければ追加しておく web-app description Sample to use JSP, Struts, Spring, Hibernate, etc for JVM stress tests with 1.3 and later. /description display-name Misc web components for tests /display-name ... index.jsp を作り、welcome アクションへのフォワードを指定する %@ taglib uri="/tags/struts-logic" prefix="logic" % logic redirect forward="welcome"/ struts-config.xml に welcome アクションを定義する global-forwards forward name="welcome" path="/Welcome.do"/ ... action-mappings action path="/Welcome" type="org.apache.struts.actions.ForwardAction" parameter="/WEB-INF/jsp/Welcome.jsp" /action ... Welcome.jsp を作成 %@ taglib uri="/tags/struts-bean" prefix="bean" % %@ taglib uri="/tags/struts-html" prefix="html" % %@ taglib uri="/tags/struts-logic" prefix="logic" % body の先頭に次のチェックを入れておく logic notPresent name="org.apache.struts.action.MESSAGE" scope="application" b ERROR Application resources not loaded -- check servlet container logs for error messages. /b /logic notPresent forward 先として使用されるのであれば次のタグも入れておく html errors/ css/global.css を作成, header 内でインクルード body {margin 0; padding 0; background #fff; text-align center; font 12px Lucida Grande , Geneva, Arial, Verdana, sans-serif; color #000;} table, td {font 10px Lucida Grande , Geneva, Verdana, Arial, sans-serif; color #000;} link rel="stylesheet" type="text/css" href="/css/global.css" media="all" 一旦デプロイして表示を確認 フォームを設置 html form action="/DirDiffCheck" focus="sourcepath" table border="0" width="100%" tr th align="right" Source /th td align="left" html text property="sourcePath"/ /td td align="left" html submit property="sourcepath_choose" value="Choose..."/ /td /tr tr th align="right" Destination /th td align="left" html text property="destPass"/ /td td align="left" html form action="/ChoosePath" html submit property="targetpath_choose" value="Choose..."/ /html form /td /tr tr td align="right" html submit property="submit" value="Submit"/ /td td align="left" html reset/ /td /tr /table /html form DirDiffCheck アクションを定義 form-beans form-bean name="ddcForm" type="app.ddcForm"/ ... action-mappings ... action path="/DirDiffCheck" name="ddcForm" type="app.DirDiffCheckAction" scope="request" validate="true" input="/WEB-INF/jsp/Welcome.jsp" forward name="success" path="/WEB-INF/jsp/Welcome.jsp"/ forward name="dchoose" path="/WEB-INF/jsp/DirChoose.jsp"/ /action app.ddcFrom を作成, ActionFrom のサブクラスとする 次のプロパティを用意する private String sourcePath; private String destPath; validate メソッドを用意する public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) { ActionErrors errors = new ActionErrors(); if ((sourcePath == null) || (sourcePath.length() 1)) { errors.add("sourcePath", new ActionMessage("error.sourcePath.required")); } if ((destPath == null) || (destPath.length() 1)) { errors.add("destPath", new ActionMessage("error.destPath.required")); } return errors; } error.sourcePath.required=Soruce path is required error.destPath.required=Dest path is required JSTL の使用 taglig 定義 %@taglib prefix="c" uri="http //java.sun.com/jstl/core"% jstl.jar, standard.jar を lib に追加 Logging commons-logging は Struts 必須のため、利用できるが、カテゴリ、レベルの 制御を考えると log4j に慣れている場合は log4j を用いたほうが早い。 また log4j.jar は WEB-INF/lib に配置する。コンテナの commons/lib では ClassNotFoundException がおきる（らしい） log4j.xml または log4j.properties は WEB-INF/classes に配置する。 log4j.xml の場合は log4j.configuration の設定がおそらく必要。 log4j.xml ?xml version="1.0" encoding="UTF-8" ? !DOCTYPE log4j configuration SYSTEM "log4j.dtd" log4j configuration xmlns log4j= http //jakarta.apache.org/log4j/ appender name="stdout" class="org.apache.log4j.ConsoleAppender" layout class="org.apache.log4j.PatternLayout" param name="ConversionPattern" value="%5p [%t] (%F %L) - %m%n"/ /layout /appender root priority value="INFO" / appender-ref ref="stdout" / /root /log4j configuration log4j.properties log4j.rootLogger=INFO, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F %L) - %m%n # log4j.rootLogger=DEBUG, stdout, rolling # log4j.appender.rolling=org.apache.log4j.RollingFileAppender # log4j.appender.rolling.File=output.log # log4j.appender.rolling.MaxFileSize=512KB # log4j.appender.rolling.MaxBackguIndex=1 # log4j.appender.rolling.layout=org.apache.log4j.PatternLayout # log4j.appender.rolling.layout.ConversionPattern=%5p [%t] (%F %L) # category setting # log4j.logging. pkg/class filter =level # log4j.logging.app.pathedit=DEBUG !!!BAD # log4j.category.app.pathedit=DEBUG JSP 内でのロギング Scriptlet の使用 %@ page import="org.apache.commons.logging.Log" % %@ page import="org.apache.commons.logging.LogFactory" % % Log logger = LogFactory.getLog(this.getClass()); % % logger.debug("This is a debug message from a jsp"); % ... % logger.info("This is another log message in the jsp"); % Log custom tag の利用 taglib taglib-uri /WEB-INF/log.tld /taglib-uri taglib-location /WEB-INF/log.tld /taglib-location /taglib このタグライブラリは log4j 依存の様だ。 % taglib uri="/WEB-INF/log.tld" prefix="logger" % logger debug message="This is a debug message from a jsp using the Log tag" / logger info message="This is another message using the log4j tag" / logger dump scope="page"/ logger dump scope="request"/ logger dump scope="session"/ logger dump scope="application"/
https://w.atwiki.jp/yuukari3/pages/14.html
Logging and Tracing in C++ Simplifiedページの翻訳版を記述します。 翻訳は、上記ページを「The翻訳インターネット V7.0LE」または「Excite 翻訳」で翻訳したものを、さらに一部簡単に修正したものです。いい日本語訳などあれば、ご指摘くださると幸いです。 簡略化された C++ のロギングとトレース By Mo Budlong, August 2001 この情報およびコードの例は好意としてSUNより提供されており、「そのまま」であり、SUNは特定の目的、または非侵害のための適応、商用のいかなる保障を含め、それに関係する全ての保証を放棄します。 概要 トレースとロギングは、デバッグの共通の支援であり、デバッグのための重要なパスです。オープンソースlog4CppパッケージはC++アプリケーションでのロギングおよびトレースのセットアップの過程を簡略化します。log4Cppについてのドキュメンテーションは、log4cppオブジェクト一式の使用についてのいくつかの簡単な例が抜けています、そして、この記事はlog4Cppの小さなバグの単純な解決方はもちろん例および説明も提供します。 ロギングとトレース あなたはトレースするべきです。。 わかりますか？あなたは確かに行います、しかし少しバックアップします。もし、あなたが500行以上のアプリケーションを書くか、アプリケーションがデーモンかサービスとして走るか、またはあなたが多くのデバッグの頭痛から自分自身を救いたいのであれば、トレースするべきです。つまり、オリジナルのステートメントを一周できます。あなたは、トレースするべきです。 ああ、しかし、C++プログラムはどのようにそのトレースを行いますか？ 手続き型言語(すなわちC)のランクを通って近づいて来たならば、恐らく老練でしょう： #ifdef DEBUG fprintf(trace_file,"Here is a useless trace messagen"); #endif しかし、オブジェクト指向言語は、うーむ・・・オブジェクトは適応させました。トレースファイルに無作為のメッセージを吐くのは全く十分上品であるというわけではありません、まさしくobjectilatedされて、objectiviedされなかった平野は言うまでもなく… 何でも。 あなたは、トレースしロギングするクラスを必要とします。 いいえ、いいえ、既に世話をされるので、それはあなたのためにここで書かれていません。 Ceki Gulcuは、log4jという名のJavaでロギングしトレースするオブジェクトの強力なセットを作成しました。 Bastiaan Bakkerは、同じセットのオブジェクトの大部分をC++に移植し、それをlog4cppと呼びます。それらは、両方ともオープンソースパッケージであり、sourceforge.net および他のオープンソースリポジトリで自由に利用可能です。 ハンマーとのみを使用して、コードが最初に著されて以来、ロギングとトレースをコードへ挿入することは周囲にありました。技術は低次技術です。しかし、それも非常に有効です。それが正確に行われる場合、ソフトウェアを監査する基礎をさらに形成し、実効誤差を記録するツールになることができます。 ロギングはプログラムを遅くすることができます。また、log4jとlog4cppの著者は緩慢を引き起こすコードの部分をぐいとひねるために非常に熱心に働きました。 マトリクスはトレースメッセージのボリュームにおける広い矛盾のために、引用するのが難しい。片端では、あなたは厳しいメッセージしかたどることができません。 #ifdef DEBUG trace("Captain, the dilithium crystals are meltingn"); #endif 他方では、コードのほとんどすべてのラインをトレースすることができます。 トレースのクラスに重要なことは、アプリケーションにおける単なる存在が過度にアプリケーションを遅くするべきでないということです。log4cppパッケージはこの点に関して優れた働きをします。 log4cppがどこで落ちるかは、ドキュメンテーションです。それぞれの個々のクラスは徹底的にドキュメント化されますが、log4cppを使用するためにどうオブジェクトを結びつけるかが少ししかもしくは何もありません。あなたがlog4jについてのドキュメンテーションを追い詰めれば、それは、log4jの使用へはじまりという1つの説となります。 したがって、ロギングとトレースに興味を持っていて、優れて、自由に利用可能なトレースツールを使用したい場合は、読み続けてでください。 log4cppは3つの主なコンポーネントを持っています カテゴリー、付加およびレイアウト。 レイアウトクラスは、出力メッセージがどのように見るかコントロールします。望む任意のスタイルの出力メッセージを指定するためにLayoutから自分のクラスを引き出してもよい。log4Cppは、2つのレイアウトクラス、SimpleLayoutおよびBasicLayoutがあります。 付加クラスはトレースメッセージをあるデバイスに書きます。メッセージはレイアウトオブジェクトによってフォーマットされています。log4Cppは標準出力、名前付きのファイル、ストリングバッファーに「追加する」クラスがあります。Appenderクラスは、Layoutのクラスと共に密接に働いています、また、もう一度、ソケット、シェアード・メモリー・バッファーあるいはある種の遅れた書き込みデバイスに記録したければ、自分のappenderクラスを引き出してもよい。log4Cppは3の有用なappendersがあります FileAppender、OstreamAppenderおよびStringQueueAppender。 カテゴリーのクラスは実際のロギングを行います。カテゴリーの2つの主要部分はそのappendersとその優先度です。優先度は、特定のクラスがどのメッセージを記録することができるかコントロールします。カテゴリーオブジェクトが作成される場合、それは標準出力の標準appenderと優先度無しで動き始めます。ログ出力先リストに、1つもしくは複数のappendersを追加することができます。瞬間に、より多くappendersが存在するでしょう。カテゴリーの優先度は、「logginess」の順序あるいは各メッセージの重要レベルの昇順に、NOTSET、DEBUG、INFO、NOTICE、WARN、ERROR、CRIT、ALERTあるいはFATAL/EMERGと設定することができます。FATALとEMERGは重要な同じ最高水準をもつ2つの名前です。各メッセージはカテゴリーオブジェクトに記録されます。カテゴリーオブジェクトは優先レベルを持っています。メッセージはそれ自身、ログにゆっくり進むようにさらに優先レベルを持っています。メッセージの優先度がカテゴリの優先度より大きな場合、あるいは等しい場合、その時、ロギングは起こります、さもなければ、メッセージが無視されます。カテゴリー優先度は下記のように並べられます： NOTSET DEBUG INFO NOTICE WARN ERROR CRIT ALERT FATAL = EMERG FATALとEMERGは等しく、最高水準です。NOTSETが最も低く、カテゴリーオブジェクトがNOTSET優先度に託される場合、それはどんなメッセージも受理し記録するでしょう。 NOTSETを除いて、これらの優先度のいずれもメッセージに与えることができます。 したがって、もしカテゴリーがWARNレベルに設定されたならば、DEBUGレベル、INFOおよびNOTICEを備えたメッセージは記録されないでしょう。 WARN、ERROR、CRIT、ALERT、FATALあるいはEMERGにセットされたメッセージが記録されるでしょう。 ルート・ノードを備えた木に配置されたカテゴリーは、トップのカテゴリーレベルになります。これは、あなたが層(カテゴリー)へトレースしながら、中断することを可能にします。子供カテゴリーは、最初に作成された時、それらの親カテゴリーの優先度を継承します。実際上、これはあまり有用ではありません。しかし、完全にはlog4Cppを訓練していません。 Appendersはカテゴリーオブジェクトに関する収集として蓄積します。 appenderがカテゴリーに加えられるとき、デフォルトの振る舞いはメッセージの記録のための、記録先リストに追加されるapenderのことである。それは、標準出力に反映させるのと同様に、同時に2ファイルへのログ/トレースをすることが可能でしょう。 実際上、あなたはめったに一度に1つを越える場所へ記録したいとは思わない、また、望む単一の目的地は、ほとんどが標準出力以外です。log4Cppは、additivityフラグを使うことで可能にします。もし、additivityプロパティが偽って設定されれば、そのとき、新しいappenderがカテゴリーオブジェクトに付けられる場合、それは目的地リストに加えられません。代わりに、それは、そのカテゴリーオブジェクト上のappendersの現在のリストを置き換えます。 このすべてがどのように結びつくでしょうか？ カテゴリークラスは1つの総合的な静的なルートカテゴリーオブジェクト(ルートと呼ばれた)を作成します。そのアプリケーションは、この1つの静的の親から子供カテゴリーのインスタンスを作成することができます。 ここに、log4Cppを使用する簡単な例があります。 もしあなたが標準出力に送られた単純なレイアウトの基礎的なロギングのセットアップを使用したくなければ、log4Cppログの使用に向けての最初の6ステップがあります appenderオブジェクト生成。 レイアウトオブジェクト生成。 appenderにレイアウトオブジェクトを付与します。 静的な関数log4cpp Category getInstance("name")を呼ぶことでカテゴリーオブジェクト生成。 追加appender(デフォルト標準出力のappenderに加えて)としてカテゴリーにappenderオブジェクトを付与する、もしくは初めにAdditivityをfalseに設定し、そのカテゴリーのための唯一のappenderとしてappenderのインストールをします。 もしあなたが単にすべてを記録したくなければ、カテゴリーのための優先度を設定してください。 // TestLog4CPP.cpp A small exerciser for log4cpp #include"Category.hh" #include"FileAppender.hh" #include"BasicLayout.hh" int main(int argc, char* argv[]) { // 1 instantiate an appender object that // will append to a log file log4cpp Appender* app = new log4cpp FileAppender("FileAppender", "/logs/testlog4cpp.log"); // 2. Instantiate a layout object // Two layouts come already available in log4cpp // unless you create your own. // BasicLayout includes a time stamp log4cpp Layout* layout = new log4cpp BasicLayout(); // 3. attach the layout object to the // appender object app- setLayout(layout); // 4. Instantiate the category object // you may extract the root category, but it is // usually more practical to directly instance // a child category log4cpp Category main_cat = log4cpp Category getInstance("main_cat"); // 5. Step 1 // an Appender when added to a category becomes // an additional output destination unless // Additivity is set to false when it is false, // the appender added to the category replaces // all previously existing appenders main_cat.setAdditivity(false); // 5. Step 2 // this appender becomes the only one main_cat.setAppender(app); // 6. Set up the priority for the category // and is given INFO priority // attempts to log DEBUG messages will fail main_cat.setPriority(log4cpp Priority INFO); // so we log some examples main_cat.info("This is some info"); main_cat.debug("This debug message will fail to write"); main_cat.alert("All hands abandon ship"); // you can log by using a log() method with // a priority main_cat.log(log4cpp Priority WARN, "This will be a logged warning"); // gives you some programmatic control over // priority levels log4cpp Priority PriorityLevel priority; bool this_is_critical = true; if(this_is_critical) priority = log4cpp Priority CRIT; else priority = log4cpp Priority DEBUG; // this would not be logged if priority // == DEBUG, because the category priority is // set to INFO main_cat.log(priority,"Importance depends on context"); // You may also log by using stream style // operations on main_cat.critStream() "This will show up as " 1 " critical message" log4cpp CategoryStream ENDLINE; main_cat.emergStream() "This will show up as " 1 " emergency message" log4cpp CategoryStream ENDLINE; // Stream operations can be used directly // with the main object, but are // preceded by the severity level main_cat log4cpp Priority ERROR "And this will be an error" log4cpp CategoryStream ENDLINE; // This illustrates a small bug in version // 2.5 of log4cpp main_cat.debug("debug");// this is correctly // skipped main_cat.info("info"); main_cat.notice("notice"); main_cat.warn("warn"); main_cat.error("error"); main_cat.crit("crit");// this prints ALERT // main_cat crit main_cat.alert("alert");// this prints PANIC // main_cat alert main_cat.emerg("emerg");// this prints UNKOWN // main_cat emerg main_cat.debug("Shutting down");// this will // be skipped // clean up and flush all appenders log4cpp Category shutdown(); return 0; } この例におけるコードの最終セクションは、log4cppの中のバグを例証します。 BasicLayout()では、メッセージは次のように記録されます date_time PRIORITY category_name message 次のリストはこのプログラムからの出力の例です。crit()メソッドが優先レベルとしてALERTを出力し、alert()メソッドが優先レベルとしてPANICを出力する、また、emerg()が優先レベルとしてUNKNOWNを出力することに注意してください。 995871335 INFO main_cat This is some info 995871335 PANIC main_cat All hands abandon ship 995871335 WARN main_cat This will be a logged warning 995871335 ALERT main_cat Importance depends on context 995871335 ALERT main_cat This will show up as 1 critical message 995871335 UNKOWN main_cat This will show up as 1 emergency message 995871335 ERROR main_cat And this will be an error 995871335 INFO main_cat info 995871335 NOTICE main_cat notice 995871335 WARN main_cat warn 995871335 ERROR main_cat error 995871335 ALERT main_cat crit 995871335 PANIC main_cat alert 995871335 UNKOWN main_cat emerg 恐らく最後の最後、オープンソースの美に行き着きます。バグは見つかりましたか？ただ進んで、それを修正してください。 次のリストは、log4cppの十分な分配の一部である、Priority.cppファイルのコピーです。 優先度の名前は静的な配列から作成され、インデックスは優先度番号に基づいて作成されます。 /* * Priority.cpp * * Copyright 2000, LifeLine Networks BV * (www.lifeline.nl). All rights reserved. * Copyright 2000, Bastiaan Bakker. All rights reserved. * See the COPYING file for the terms of usage and * distribution. */ #include "Portability.hh" #include "Priority.hh" namespace log4cpp { const std string Priority getPriorityName(int priority) throw() { static std string names[9] = { "PANIC", "ALERT", "ERROR", "WARN", "NOTICE", "INFO", "DEBUG", "NOTSET", "UNKOWN" }; priority++; priority /= 100; return (*1) ? names[8] names[priority - 1]; } } しかし、優先順位番号は、この機能がPriority.hhからの抜粋で以下に示すように予期するより、わずかに異なります。 typedef enum { EMERG = 0, FATAL = 0, ALERT = 100, CRIT = 200, ERROR = 300, WARN = 400, NOTICE = 500, INFO = 600, DEBUG = 700, NOTSET = 800 } PriorityLevel; したがって、修正は以下のように(変更が強調されます)配列とコードを調節することです。 /* * Priority.cpp * * Copyright 2000, LifeLine Networks BV (www.lifeline.nl). * All rights reserved. * Copyright 2000, Bastiaan Bakker. All rights reserved. * * See the COPYING file for the terms of usage and * distribution. */ #include "Portability.hh" #include "Priority.hh" namespace log4cpp { const std string Priority getPriorityName(int priority) throw() { static std string names[10] = { "PANIC", "ALERT", "CRITICAL", "ERROR", "WARN", "NOTICE", "INFO", "DEBUG", "NOTSET", "UNKOWN" }; priority++; priority /= 100; return (*2) ? names[9] names[priority]; } } log4cppは非常に柔軟で親しみがあります。あなたが望むすべての方法および多数の出力先へのログをフォーマットするためにそれを修正することができます。それは多くのプロジェクトで、あなたから多くの開発時間を省くでしょう。Bakker氏に敬意を評します。 log4Cppは、まだまだ欠けている１つの重大な断片です。Javaバージョンlog4jは、コードを修正する必要なしに、プログラムの「logginess」を変更することができるようなXMLまたは他の設定ファイルから構成をとるConfiguratorクラスを含んでいました。これはlog4cppへのダイナマイトな追加になるでしょう。 これは何か考えをあなたに与えますか? リソース sourceforge.netはオープンソースソフトウェアのための素晴らしいリソースです。 log4cppと log4jと同様に、あなたはPerlのためのlog4p、Pythonのための別の log4p、および log4dなど、デルフォイのための同様の口ギング機能を作成するための進行中のプロジェクトを見つけるでしょう。 log4jの使用への入門、およびlog4cppに対して適用性を持っている他のドキュメンテーションは、The JakartaProjectにあります。 著者に関して Mo BudlongはKing Computer Servicesの社長で、15年以上の間UNIX(R) boxesの上のユーティリィティ、アプリケーションおよびクライアントサーバソリューションを作成しています。彼は、アセンブリ言語からXMLにまで及び、それらを対象に多数の本および記事を出版しました。彼はウェブ・ベースのUNIX 101カラムの著者で、すぐにUNIX basicsについての本を出版しています。さらに、Moは、ギター、バスおよびキーボードを演奏し、他のいくつかの楽器をいじる音楽家です。彼は、妻、娘および猫と南カリフォルニアで暮らします。 2001年8月 名前 コメント
https://w.atwiki.jp/aias-closurecompiler/pages/25.html
トップページ Closure Compiler Application Closure Compiler Application コマンドラインオプション このページでは、Closure Comiler Applicationのコマンドラインオプションについて詳細に説明します。Closure Comiler Applicationの使用方法についてはこちらを参照してください。 このページは--helpオプションで出力されるヘルプの情報を元に作成しました。尚、管理人が使い方を理解できなかったオプションについてはヘルプの原文（英語）をそのまま記載しています。 目次 主なオプション --charset --compilation_level --externs --formatting --help --js --js_output_file --manage_closure_dependencies --use_only_custom_externs --warning_level その他のオプション --compute_phase_ordering --create_name_map_files --create_source_map --debug --define (--D, -D) --jscomp_dev_mode (--dev_mode) --jscomp_error --jscomp_off --jscomp_warning --logging_level --module --module_output_path_prefix --module_wrapper --output_manifest --output_wrapper --output_wrapper_marker --print_ast --print_pass_graph --print_tree --process_closure_primitives --property_map_input_file --property_map_output_file --summary_detail_level --third_party --variable_map_input_file --variable_map_output_file 主なオプション --charset --charset VAL 全ての入力ファイルの文字エンコーディングを指定します。（入力ファイルは全て同じ文字エンコーディングを使用していなくてはなりません。）省略した場合、ファイルの文字エンコーディングは UTF-8 であると解釈されます。 --compilation_level --compilation_level [WHITESPACE_ONLY|SIMPLE_OPTIMIZATIONS|ADVANCED_OPTIMIZATIONS] JavaScriptに適用する圧縮と最適化の度合い（コンパイルレベル）を指定します。以下の３つのレベルがあります： WHITESPACE_ONLY JavaScriptから空白・改行とコメントだけを削除します。 SIMPLE_OPTIMIZATIONS WHITESPACE_ONLY での処理に加えてローカル変数のリネームを行い、コードの圧縮と最適化を行います。このレベルではコンパイルされたコードとそれ以外のコードとの連携が妨げられることはありません。 ADVANCED_OPTIMIZATIONS SIMPLE_OPTIMIZATIONS での処理に加えてグローバル領域を含むシンボルのリネームを行い、最高レベルの圧縮度を実現します。 ADVANCED_OPTIMIZATIONS を使用する場合、外部のシンボルとの参照関係を維持するために追加の手順を実行する必要があります。 ADVANCED_OPTIMIZATIONS レベルのコンパイル処理が求める様々な制約については、こちらを参照してください。 オプション指定を省略した場合は SIMPLE_OPTIMIZATIONS が適用されます。 --externs --externs VAL コンパイル対象となっていないコード上で定義されたシンボル名がリネームされるのを防ぐためのexternファイルを指定します。このオプションが効果をもつのはcompilation_levelオプションの値が ADVANCED_OPTIMIZATIONS の場合のみです。externに関して詳しくはこちらを参照してください。 複数のexternファイルがある場合はこのオプションを複数指定してください。 --formatting --formatting [pretty_print|print_input_delimiter] 出力されるコンパイル済みJavaScriptコードの整形方式を指定します。このオプションは pretty_print または print_input_delimiter のどちらかの値をとりますが、２つの formatting オプションによってこれらを同時に指定することが可能です。 pretty_print と print_input_delimiter は整形方法のそれぞれ異なる側面についての指示であるため、重複しても互いに影響しあうことがありません。 pretty_print 人間が読み易くなるよう出力コードに改行とインデントを付加します。以下にその例を示します： function hello(a) { alert("Hello, " + a) } hello("New user"); pretty_print がない場合は次のようになります。 function hello(a){alert("Hello, "+a)}hello("New user"); print_input_delimiter 各入力ファイルの範囲を示す文字列を出力コード内に付加します。例えば2つのファイルを一緒にコンパイルした場合、出力は次のようになります： // Input 0 alert("hi"); // Input 1 alert("bye"); ファイル間の境界を表す区切り文字としてClosure Compilerは「 // Input X 」を挿入します。これらの区切り文字はコメントであり、JavaScriptの動作を妨げない点に注意してください。入力ファイルの区切りには、例えば各ファイルのサイズ圧縮度の把握を助けるというような用途が考えられます。 --help --help コンソールにオプションのリストを表示し、処理を終了します。 --js --js VAL 入力JavaScriptファイル名を指定します。複数の入力ファイルがある場合はオプションを複数指定してください。このオプションが未指定の場合、出力結果は空文字列となります。 --js_output_file --js_output_file VAL 出力ファイル名を指定します。省略した場合、処理結果は標準出力に出力されます。 --manage_closure_dependencies --manage_closure_dependencies [true|false] true を指定した場合、 goog.provide で定義されたシンボルは必ずそれを要求する goog.require より前に存在する、という関係に基づいて自動的にファイルのソートを実行します。もし定義されたシンボルが一度も要求されなかった場合、そのシンボルはコンパイル結果から除外されます。このオプションの詳細についてはこちらを参照してください。デフォルトは false です。 --use_only_custom_externs --use_only_custom_externs [true|false] Closure Compilerは document オブジェクトやそのメソッドのような標準的なシンボルを宣言したexternファイルを持っており、デフォルトではそれを使用してシンボル名の保護を行います。 --use_only_custom_externs オプションに true を指定するとこれらの標準的なexternを使用しなくなります。デフォルトのextern宣言に関する詳細はこちらを参照してください。デフォルトは false です。 --warning_level --warning_level [QUIET|DEFAULT|VERBOSE] コード内の問題になりそうな箇所に関する情報の量を指定します。警告レベルには以下の３種類があります： QUIET 現在のコンパイルでのcompilation_levelに基づく最適化パスで生成された文法エラーと警告のみを出力します。 DEFAULT 最適化パスで生成された文法エラーと警告に加え、選択されたコードチェックパス上で生成された警告を出力します。 warning_level オプションのデフォルト値です。 VERBOSE 最適化パスで生成された文法エラーと警告に加え、実行された全てのコードチェックパス上で生成された警告を出力します。 エラーと警告は標準エラー出力に出力されます。 その他のオプション --compute_phase_ordering --compute_phase_ordering Runs the compile job many times, then prints out the best phase ordering from this run. --create_name_map_files --create_name_map_files [true|false] If true, variable renaming and property renaming map files will be produced as {binary name}_vars_map.out and {binary name}_props_map.out. Note that this flag cannot be used in conjunction with either variable_map_output_file or property_map_output_file. --create_source_map --create_source_map VAL Closure Inspectorのソースマッピング機能で使用するソースマップファイルの出力ファイルパスを指定します。ソースマップファイルにはコンパイルされたコードとオリジナルのコードとの位置関係がマッピングされています。指定に %output% という文字列を含めると、それはコンパイル結果の出力ファイル名がその位置に展開されるプレースホルダとして機能します。 --debug --debug [true|false] true を指定するとデバッグ用の出力を行ないます。デフォルトは false です。 --define (--D, -D) --define (--D, -D) VAL @define タグが付けられた変数を指定の値で上書きします。このオプションの値の書式は name [= val ] で、 name には @define タグが付与された変数の名前を、 val には置き換えたい値を指定します。 val の値にはブール値、数値、シングルクォートされた文字列（ただしシングルクォートを含まない）を使用できます。 val が省略された場合は true が適用されます。 このオプションについてはこちらも参照してください。 --jscomp_dev_mode (--dev_mode) --jscomp_dev_mode (--dev_mode) [OFF|START|START_AND_END|EVERY_PASS] Turns on extra sanity checks. --jscomp_error --jscomp_error VAL Make the named class of warnings an error. Options accessControls, checkRegExp, checkTypes, checkVars, deprecated, fileoverviewTags, invalidCasts, missingProperties, nonStandardJsDocs, strictModuleDepCheck, undefinedVars, unknownDefines, visibility --jscomp_off --jscomp_off VAL Turn off the named class of warnings. Options accessControls, checkRegExp, checkTypes, checkVars, deprecated, fileoverviewTags, invalidCasts, missingProperties, nonStandardJsDocs, strictModuleDepCheck, undefinedVars, unknownDefines, visibility --jscomp_warning --jscomp_warning VAL Make the named class of warnings a normal warning. Options accessControls, checkRegExp,checkTypes, checkVars, deprecated, fileoverviewTags, invalidCasts, missingProperties, nonStandardJsDocs, strictModuleDepCheck, undefinedVars, unknownDefines, visibility --logging_level --logging_level VAL The logging level (standard java.util.logging.Level values) for Compiler progress. Does not control errors or warnings for the JavaScript code under compilation. --module --module VAL A javascript module specification. The format is name num-js-files [ [ dep ,...][ ]]]. Module names must be unique. Each dep is the name of a module that this module depends on. Modules must be listed in dependency order, and js source files must be listed in the corresponding order. Where --module flags occur in relation to --js flags is unimportant --module_output_path_prefix --module_output_path_prefix VAL Prefix for filenames of compiled js modules. module-name .js will be appended to this prefix. Directories will be created as needed. Use with --module. --module_wrapper --module_wrapper VAL An output wrapper for a javascript module (optional). The format is name wrapper . The module name must correspond with a module specified using --module. The wrapper must contain %s as the code placeholder. --output_manifest --output_manifest VAL 値としてファイル名を指定し、コンパイルされた全てのファイルのリストをそこに出力します。--manage_closure_dependenciesオプションが有効な場合、使用されなかったためにコンパイル対象にならなかったファイルはリストから除外されます。The %outname% placeholder expands to the js output file. If you re using modularization, using %outname% will create a manifest for each module. このオプションについてはこちらも参照してください。 --output_wrapper --output_wrapper VAL このオプションに指定された文字列にコンパイル結果を内包して出力させます。以下に例を示します： --output_wrapper (function(){%output%})() %output% がコンパイルされたコードのプレースホルダとなります。上のような形式で出力するとコンパイルされたコードのスコープは外側の関数内に限定されるため、リネームされたシンボルによるグローバル領域の汚染を防止することができます。デフォルトのプレースホルダ %output% は--output_wrapper_markerによって任意の文字列に変更できます。 --output_wrapper_marker --output_wrapper_marker VAL --output_wrapperオプションにおいてコンパイルされたコードのプレースホルダとして使用されるトークン文字列を指定します。 --print_ast --print_ast Prints a dot file describing the internal abstract syntax tree and exits. --print_pass_graph --print_pass_graph Prints a dot file describing the passes that will get run and exits. --print_tree --print_tree Prints out the parse tree and exits. --process_closure_primitives --process_closure_primitives [true|false] goog.require() 、 goog.provide() 、 goog.exportSymbol() のようなClosure Libraryの関数をコンパイル時にコードに展開します。デフォルトは true です。 ヘルプには上のように書かれていますが、管理人の試した限りでは展開されるのは goog.require() と goog.provide() だけのようでした。 --property_map_input_file --property_map_input_file VAL File containing the serialized version of the property renaming map produced by a previous compilation. --property_map_output_file --property_map_output_file VAL File where the serialized version of the property renaming map produced should be saved. --summary_detail_level --summary_detail_level N Controls how detailed the compilation summary is. Values 0 (never print summary), 1 (print summary only if there are errors or warnings), 2 (print summary if type checking is on, see --check_types), 3 (always print summary). The default level is 1. --third_party --third_party Check source validity but do not enforce Closure style rules and conventions. --variable_map_input_file --variable_map_input_file VAL File containing the serialized version of the variable renaming map produced by a previous compilation. --variable_map_output_file --variable_map_output_file VAL File where the serialized version of the variable renaming map produced should be saved.
https://w.atwiki.jp/syusei/pages/13.html
log4j.propetiesのサンプル log4j.rootCategory=INFO, STDOUT # stdout log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout log4j.appender.STDOUT.layout.ConversionPattern=%d{HH mm ss} %-5p %m (%c)%n
https://w.atwiki.jp/pjkyt/pages/15.html
日本語 What s this? As far as I know, Android SDK has no offering of standard FileDialog as it exists for Java SE. I thought it might help to make something simple available. It s just a toy code. Feel free to do anything with it. Download What it does It works in four modes 1. Select file 2. Create file 3. Select directory 4. Create directory In mode 1 and 3, the file dialog have the user select existing file / directory. User can navigate through the file system up and down and tap on the desired the file (Figure 1). In case of selecting directory, user can press Here to specify the current directory. In mode 2 and 4, the file dialog have the user enter the new file / directory name that he wishes to create. User can navigate through the file system up and down and tap Here to designate where the file should be created (Figure 2). Then a text box dialog appears and asks for the new file / directory name (Figure 3). In case a file is selected, the text box is brought up with the selected file name filled in. How it works Here s an example code you ll find in the download package. The code inside onCreate() corresponds to the four mode explained above. The first argument is the initial directory. The second and third controls the mode. And the fourth and fifth passes the Context and FileDialogue.Listener. FileDialogue.Listener must be implemented to receive the result from FileDialogue. fd.showDialogue() launches the dialog box. When user has made selection, onSelected() is invoked with the directory and file name as an argument (filename will be "" when ). Else when user has pressed the "back" button, onCanceled() is invoked. That s it! public class FdExample extends Activity implements FileDialogue.Listener { /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); // (1) Select file, starting direcotry is /sdcard/ FileDialogue fd = new FileDialogue(null, FileDialogue.FILE, FileDialogue.SELECT, this, this); // (2) Create file, starting direcotry is /sdcard/, user will be requested to enter filename // FileDialogue fd = new FileDialogue("/sdcard/picture/", FileDialogue.FILE, FileDialogue.CREATE, this, this); // (3) Select directory, starting direcotry is /sdcard // FileDialogue fd = new FileDialogue(null, FileDialogue.DIRECTORY, FileDialogue.SELECT, this, this); // (4) Create directory, starting direcotry is /sdcard/, user will be requested to enter direcotry name // FileDialogue fd = new FileDialogue(null, FileDialogue.DIRECTORY, FileDialogue.CREATE, this, this); fd.showDialogue(); } public void onSelected(String directory, String filename) { // filename will be "" when target is the FileDialogue.DIRECOTRY Log.v("FdExample", "Directory = " + directory + ", File = " + filename); } public void onCanceled() { // this is when "back" button is pressed Log.v("FdExample", "Canceled"); } } Is this as good as it gets? Actually, I had never liked the file dialog in general. It is rather tiring to use it. As it is launched, I must resolve where I am now and plan how I should travel to the objective location. It s a lot of screen interpretation, a lot of structural memory challenge, and not even a hint of joy. It it one UI scheme that abuses the weak parts of the human capability. So we have some idea going. We are thinking we can create a better alternative that can take advantage of parallel processing of visual image and geometric / chromatic memory -- human is much better at those. It will be quick to get desired location, much less stressful to use, and hopefully fun. I hope we can implement the idea quickly and make available through this wiki soon. アルバイトはじめましたd(´∀｀*)グッ♪ http //www.e29.mobi/ -- (わかりません) 2012-01-05 04 12 48 名前 コメント すべてのコメントを見る
https://w.atwiki.jp/mynote/pages/11.html
IntelMacでPovray IntelMacではPovrayが起動時に突然終了してしまうので、UNIX版を落として来て readmeファイルにある通り ======================== Compiling and installing ======================== Basic and detailed instructions to compile and install the generic POV-Ray source code on UNIX-based systems are given in the INSTALL file. In a nutshell the package installation is based on a configure script which detects your environment automatically and adapts the compilation and installation process accordingly. Simply run % ./configure COMPILED_BY="your name email@address " # configure the package % make # build the program % su # log as root $ make install # install program + data Please consult the INSTALL file for further details. POV-Ray 3.5 was the first effort at an official version of POV-Ray using a configure script and Makefiles generated by the GNU autoconf and automake tools. In POV-Ray 3.6 the configure script and accompanying files have been completely rewritten to work with as many platforms as possible, including systems that are missing some required libraries; see below. We hope that not only Linux but many (if not all) UNIX-based platforms will benefit from the new configure script. 449 cat readme 450 ./configure 451 ./configure COMPILED_BY="xxxx xxxx@xxxx.co.jp " 452 make 453 su 454 make install ではInstallできない、Macの場合はX11でsuでrootになり、 yama07 /Users/macmini/povray$ su Password yama07 /Users/macmini/povray root#make install で〜〜/povray/unixディレクトリに[povray]ってのが できてるから、 cp povray /sw/bin でおk $povray で実行できる レタリング 作業ディレクトリに行き $ povray test.pov でレタリングしてくれる オプションとして+W,+H等がある オプション一覧？（ただのコピペ） Parsing options I name = input file name HI name = header include file name L name = library path prefix MVn.n = set compability to version n.n SU = split bounded unions if children are finite UR = remove unnecessary bounding objects Output options Hn = image height of n pixels Wn = image width of n pixels SRn|0.n = start at row n | start row at n percent of image ERn|0.n = end at row n | end row at n percent of image SCn|0.n = start at col n | start col at n percent of image ECn|0.n = end at col n | end col at n percent of image C = continue aborted trace P = pause before exit V = verbose messages on WLn = set warning level to n X[n] = enable early exit by key hit (every n pixels) Output options - display related D[xy] = display rendering (in format x, using palette option y) SPn = display mosaic preview, start grid size = 2, 4, 8, 16, ... EPn = display mosaic preview, end grid size = 2, 4, 8, 16, ... UD = draw vista rectangles Output options - file related B[n] = Use buffer (of n KB) for output file F[x] = write output file (in format x) FC - Compressed Targa with 24 or 32 bpp FN[n] - PNG (n bits/color, n = 5 to 16, default is 8) FP - PPM FS - System specific FT - Uncompressed Targa with 24 or 32 bpp O name = output file name HTx = write CPU utilization histogram in format x HTC - Comma separated values (CSV - spreadsheet) HTN - PNG grayscale HTP - PPM heightfield HTS - System specific HTT - Uncompressed TGA heightfield HTX - No histogram output HN name = histogram filename HSx.y = histogram grid number of x, y divisions Tracing options MB[n] = use bounding slabs (if more than n objects) Qn = image quality (0 = rough, 9 = full) A[0.n] = perform antialiasing (if color change is above n percent) AMn = use non-adaptive (n=1) or adaptive (n=2) supersampling J[n.n] = set antialiasing-jitter (and amount) Rn = set antialiasing-depth (use n X n rays/pixel) UA = use alpha channel UL = use light buffer UV = use vista buffer Animation options Kn.n = set frame clock to n.n KFIn = set initial frame number to n KFFn = set final frame number to n KIn.n = set initial clock value to n.n KFn.n = set final clock value to n.n SFn|0.n = start subset at frame n | start at n percent in sequence EFn|0.n = end subset at frame n | end at n percent in sequence KC = calculate clock value for cyclic animation UF = use field rendering UO = use odd lines in odd frames Redirecting options GI name = write all .INI parameters to file name Gx name = write stream x to console (and/or optional file name) GA - All streams (except status) GD - Debug stream GF - Fatal stream GR - Render stream GS - Statistics stream GW - Warning stream オプション一覧？（ちょっと通訳） Parsing options（構造オプション） I name = インプットするファイルネーム $ povray test.pov でも可能だが $ povray +I test.pov が正式？ HI name = header include file name L name = いつも呼び込むライブラリがあるディレクトリパス library path prefix MVn.n = set compability to version n.n SU = split bounded unions if children are finite UR = remove unnecessary bounding objects Output options Hn = Outputイメージファイルの高さ指定image height of n pixels Wn = Outputイメージファイルの高さ指定image width of n pixels $ povray test.pov +W640 +H480 デフォルトでは幅320pix,高さ240pixになってます SRn|0.n = start at row n | start row at n percent of image ERn|0.n = end at row n | end row at n percent of image SCn|0.n = start at col n | start col at n percent of image ECn|0.n = end at col n | end col at n percent of image C = continue aborted trace P = pause before exit V = verbose messages on WLn = set warning level to n X[n] = enable early exit by key hit (every n pixels) Output options - display related D[xy] = display rendering (in format x, using palette option y) SPn = display mosaic preview, start grid size = 2, 4, 8, 16, ... EPn = display mosaic preview, end grid size = 2, 4, 8, 16, ... UD = draw vista rectangles Output options - file related B[n] = Use buffer (of n KB) for output file F[x] = write output file (in format x) FC - Compressed Targa with 24 or 32 bpp +FC 24ビットTGA圧縮ファイル $povray +FC source.pov FN[n] - PNG (n bits/color, n = 5 to 16, default is 8) +FN 24ビットPNGファイル $povray +FN[8] source.pov FP - PPM +FP 24ビットPPMファイル $povray +FP source.pov FS - System specific +FS システム標準（Windows：BMP,Mac PNG,Linux PNG）[デフォルト] $povray source.pov -これでO.K FT - Uncompressed Targa with 24 or 32 bpp +FT 24ビットTGA非圧縮ファイル $povray +FT source.pov O name = output file name HTx = write CPU utilization histogram in format x HTC - Comma separated values (CSV - spreadsheet) HTN - PNG grayscale HTP - PPM heightfield HTS - System specific HTT - Uncompressed TGA heightfield HTX - No histogram output HN name = histogram filename HSx.y = histogram grid number of x, y divisions Tracing options MB[n] = use bounding slabs (if more than n objects) Qn = image quality (0 = rough, 9 = full) A[0.n] = perform antialiasing (if color change is above n percent) AMn = use non-adaptive (n=1) or adaptive (n=2) supersampling J[n.n] = set antialiasing-jitter (and amount) Rn = set antialiasing-depth (use n X n rays/pixel) UA = use alpha channel UL = use light buffer UV = use vista buffer Animation options Kn.n = set frame clock to n.n KFIn = set initial frame number to n KFFn = set final frame number to n $ povray test.pov +KFF100 clock関数？を使った時test001.png~test100.png まで100個の静止画ファイルを作る KIn.n = set initial clock value to n.n KFn.n = set final clock value to n.n SFn|0.n = start subset at frame n | start at n percent in sequence EFn|0.n = end subset at frame n | end at n percent in sequence KC = calculate clock value for cyclic animation UF = use field rendering UO = use odd lines in odd frames Redirecting options GI name = write all .INI parameters to file name Gx name = write stream x to console (and/or optional file name) GA - All streams (except status) GD - Debug stream GF - Fatal stream GR - Render stream GS - Statistics stream GW - Warning stream LAM-MPIを使用してコンパイル、リンクしたparapovがうまく走らん（以下Error） [cfd@utmcc010 advanced]$ mpirun -np 4 povray benchmark.pov Warning Warning Could not set priority Success Could not set priority Success Persistence of Vision(tm) Ray Tracer Version 3.5 Unix (.Linux.gcc) This is an unofficial version compiled by Benajmin Goldbach benny.goldbach@t-online.de and Matthias Fueller matthias_fueller@web.de - ParaPov Version 1.0 The POV-Ray Team(tm) is not responsible for supporting this version. Copyright 1991-2002 POV-Ray Team(tm) This is Parapov V1.0, a parallel extension to povray Warning Could not set priority Success Parsing Options Input file benchmark.pov (compatible to version 3.5) Remove bounds........On Split unions........Off Library paths /usr/local/share/povray-3.5 /usr/local/share/povray-3.5/include Output Options Image resolution 320 by 240 (rows 1 to 240, columns 1 to 320). Output file benchmark.png, 24 bpp PNG Graphic display......On (type 0, palette 3, gamma 2.2) Mosaic preview......Off CPU usage histogram.Off Continued trace.....Off Allow interruption..Off Pause when done.....Off Verbose messages.....On Tracing Options Quality 9 Bounding boxes.......On Bounding threshold 3 Light Buffer.........On Vista Buffer.........On Draw Vista Buffer...Off Antialiasing........Off Animation Options Clock value.... 0.000 (Animation off) ParaPov Options Block Width.......32 Block Height......32 Client Niceness...5 Client Logging....On Redirecting Options All Streams to console.........Off Debug Stream to console.........On Fatal Stream to console.........On Render Stream to console........On Statistics Stream to console....On Warning Stream to console.......On Starting frame 0... Displaying frame 0...Xlib connection to " 0.0" refused by server Xlib No protocol specified File Init Error The display 0.0 is not a valid display, MPI_Recv process in local group is dead (rank 1, comm 3) Rank (2, MPI_COMM_WORLD) Call stack within LAM Rank (2, MPI_COMM_WORLD) - MPI_Recv() Rank (2, MPI_COMM_WORLD) - MPI_Barrier() Rank (2, MPI_COMM_WORLD) - MPI_Barrier() Rank (2, MPI_COMM_WORLD) - main() One of the processes started by mpirun has exited with a nonzero exit code. This typically indicates that the process finished in error. If your process did not finish in error, be sure to include a "return 0" or "exit(0)" in your C code before exiting the application. PID 32069 failed on node n0 (202.13.13.16) due to signal 13. MPI_Recv process in local group is dead (rank 1, SSI coll smp local comm for CID 0) Rank (3, MPI_COMM_WORLD) Call stack within LAM Rank (3, MPI_COMM_WORLD) - MPI_Recv() Rank (3, MPI_COMM_WORLD) - MPI_Bcast() Rank (3, MPI_COMM_WORLD) - MPI_Barrier() Rank (3, MPI_COMM_WORLD) - main() [cfd@utmcc010 advanced]$ date 2007年 1月 4日 木曜日 22 00 18 JST
https://w.atwiki.jp/reisiki/pages/87.html
# Doxyfile 1.5.8 # This file describes the settings to be used by the documentation system# doxygen (www.doxygen.org) for a project## All text after a hash (#) is considered a comment and will be ignored# The format is # TAG = value [value, ...]# For lists items can also be appended using # TAG += value [value, ...]# Values that contain spaces should be placed between quotes (" ") #---------------------------------------------------------------------------# Project related configuration options#--------------------------------------------------------------------------- # This tag specifies the encoding used for all characters in the config file # that follow. The default is UTF-8 which is also the encoding used for all # text before the first occurrence of this tag. Doxygen uses libiconv (or the # iconv built into libc) for the transcoding. See # http //www.gnu.org/software/libiconv for the list of possible encodings. DOXYFILE_ENCODING = UTF-8 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded # by quotes) that should identify the project. PROJECT_NAME = siki # The PROJECT_NUMBER tag can be used to enter a project or revision number. # This could be handy for archiving the generated documentation or # if some version control system is used. PROJECT_NUMBER = ver.090625 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # base path where the generated documentation will be put. # If a relative path is entered, it will be relative to the location # where doxygen was started. If left blank the current directory will be used. OUTPUT_DIRECTORY = docs # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create # 4096 sub-directories (in 2 levels) under the output directory of each output # format and will distribute the generated files over these directories. # Enabling this option can be useful when feeding doxygen a huge amount of # source files, where putting all generated files in the same directory would # otherwise cause performance problems for the file system. CREATE_SUBDIRS = NO # The OUTPUT_LANGUAGE tag is used to specify the language in which all # documentation generated by doxygen is written. Doxygen will use this # information to generate all constant output in the proper language. # The default language is English, other supported languages are # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, # Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, # Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), # Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, # Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, # Spanish, Swedish, and Ukrainian. OUTPUT_LANGUAGE = Japanese # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will # include brief member descriptions after the members that are listed in # the file and class documentation (similar to JavaDoc). # Set to NO to disable this. BRIEF_MEMBER_DESC = YES # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend # the brief description of a member or function before the detailed description. # Note if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the # brief descriptions will be completely suppressed. REPEAT_BRIEF = YES # This tag implements a quasi-intelligent brief description abbreviator # that is used to form the text in various listings. Each string # in this list, if found as the leading text of the brief description, will be # stripped from the text and the result after processing the whole list, is # used as the annotated text. Otherwise, the brief description is used as-is. # If left blank, the following values are used ("$name" is automatically # replaced with the name of the entity) "The $name class" "The $name widget" # "The $name file" "is" "provides" "specifies" "contains" # "represents" "a" "an" "the" ABBREVIATE_BRIEF = # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then # Doxygen will generate a detailed section even if there is only a brief # description. ALWAYS_DETAILED_SEC = NO # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all # inherited members of a class in the documentation of that class as if those # members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. INLINE_INHERITED_MEMB = YES # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full # path before files name in the file list and in the header files. If set # to NO the shortest path that makes the file name unique will be used. FULL_PATH_NAMES = NO # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag # can be used to strip a user-defined part of the path. Stripping is # only done if one of the specified strings matches the left-hand part of # the path. The tag can be used to show relative paths in the file list. # If left blank the directory from which doxygen is run is used as the # path to strip. STRIP_FROM_PATH = # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of # the path mentioned in the documentation of a class, which tells # the reader which header file to include in order to use a class. # If left blank only the name of the header file containing the class # definition is used. Otherwise one should specify the include paths that # are normally passed to the compiler using the -I flag. STRIP_FROM_INC_PATH = # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter # (but less readable) file names. This can be useful is your file systems # doesn t support long names like on DOS, Mac, or CD-ROM. SHORT_NAMES = NO # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen # will interpret the first line (until the first dot) of a JavaDoc-style # comment as the brief description. If set to NO, the JavaDoc # comments will behave just like regular Qt-style comments # (thus requiring an explicit @brief command for a brief description.) JAVADOC_AUTOBRIEF = NO # If the QT_AUTOBRIEF tag is set to YES then Doxygen will # interpret the first line (until the first dot) of a Qt-style # comment as the brief description. If set to NO, the comments # will behave just like regular Qt-style comments (thus requiring # an explicit \brief command for a brief description.) QT_AUTOBRIEF = NO # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen # treat a multi-line C++ special comment block (i.e. a block of //! or /// # comments) as a brief description. This used to be the default behaviour. # The new default is to treat a multi-line C++ comment block as a detailed # description. Set this tag to YES if you prefer the old behaviour instead. MULTILINE_CPP_IS_BRIEF = NO # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented # member inherits the documentation from any documented member that it # re-implements. INHERIT_DOCS = YES # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce # a new page for each member. If set to NO, the documentation of a member will # be part of the file/class/namespace that contains it. SEPARATE_MEMBER_PAGES = NO # The TAB_SIZE tag can be used to set the number of spaces in a tab. # Doxygen uses this value to replace tabs by spaces in code fragments. TAB_SIZE = 8 # This tag can be used to specify a number of aliases that acts # as commands in the documentation. An alias has the form "name=value". # For example adding "sideeffect=\par Side Effects \n" will allow you to # put the command \sideeffect (or @sideeffect) in the documentation, which # will result in a user-defined paragraph with heading "Side Effects ". # You can put \n s in the value part of an alias to insert newlines. ALIASES = # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C # sources only. Doxygen will then generate output that is more tailored for C. # For instance, some of the names that are used will be different. The list # of all members will be omitted, etc. OPTIMIZE_OUTPUT_FOR_C = NO # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java # sources only. Doxygen will then generate output that is more tailored for # Java. For instance, namespaces will be presented as packages, qualified # scopes will look different, etc. OPTIMIZE_OUTPUT_JAVA = NO # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran # sources only. Doxygen will then generate output that is more tailored for # Fortran. OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for # VHDL. OPTIMIZE_OUTPUT_VHDL = NO # Doxygen selects the parser to use depending on the extension of the files it parses. # With this tag you can assign which parser to use for a given extension. # Doxygen has a built-in mapping, but you can override or extend it using this tag. # The format is ext=language, where ext is a file extension, and language is one of # the parsers supported by doxygen IDL, Java, Javascript, C#, C, C++, D, PHP, # Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), # use inc=Fortran f=C EXTENSION_MAPPING = # If you use STL classes (i.e. std string, std vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should # set this tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std string); v.s. # func(std string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. BUILTIN_STL_SUPPORT = YES # If you use Microsoft s C++/CLI language, you should set this option to YES to # enable parsing support. CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. # Doxygen will parse them like normal C++ but will assume all classes use public # instead of private inheritance when no explicit protection keyword is present. SIP_SUPPORT = NO # For Microsoft s IDL there are propget and propput attributes to indicate getter # and setter methods for a property. Setting this option to YES (the default) # will make doxygen to replace the get and set methods by a property in the # documentation. This will only work if the methods are indeed getting or # setting a simple type. If this is not the case, or you want to show the # methods anyway, you should set this option to NO. IDL_PROPERTY_SUPPORT = YES # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC # tag is set to YES, then doxygen will reuse the documentation of the first # member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. DISTRIBUTE_GROUP_DOC = NO # Set the SUBGROUPING tag to YES (the default) to allow class member groups of # the same type (for instance a group of public functions) to be put as a # subgroup of that type (e.g. under the Public Functions section). Set it to # NO to prevent subgrouping. Alternatively, this can be done per class using # the \nosubgrouping command. SUBGROUPING = YES # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum # is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # with name TypeT. When disabled the typedef will appear as a member of a file, # namespace, or class. And the struct will be named TypeS. This can typically # be useful for C code in case the coding convention dictates that all compound # types are typedef ed and only the typedef is referenced, never the tag name. TYPEDEF_HIDES_STRUCT = NO # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to # determine which symbols to keep in memory and which to flush to disk. # When the cache is full, less often used symbols will be written to disk. # For small to medium size projects ( 1000 input files) the default value is # probably good enough. For larger projects a too small cache size can cause # doxygen to be busy swapping symbols to and from disk most of the time # causing a significant performance penality. # If the system has enough physical memory increasing the cache will improve the # performance by keeping more symbols in memory. Note that the value works on # a logarithmic scale so increasing the size by one will rougly double the # memory usage. The cache size is given by this formula # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, # corresponding to a cache size of 2^16 = 65536 symbols SYMBOL_CACHE_SIZE = 0 #---------------------------------------------------------------------------# Build related configuration options#--------------------------------------------------------------------------- # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in # documentation are documented, even if no documentation was available. # Private class members and static file members will be hidden unless # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES EXTRACT_ALL = NO # If the EXTRACT_PRIVATE tag is set to YES all private members of a class # will be included in the documentation. EXTRACT_PRIVATE = YES # If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. EXTRACT_STATIC = YES # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) # defined locally in source files will be included in the documentation. # If set to NO only classes defined in header files are included. EXTRACT_LOCAL_CLASSES = YES # This flag is only useful for Objective-C code. When set to YES local # methods, which are defined in the implementation section but not in # the interface are included in the documentation. # If set to NO (the default) only methods in the interface are included. EXTRACT_LOCAL_METHODS = YES # If this flag is set to YES, the members of anonymous namespaces will be # extracted and appear in the documentation as a namespace called # anonymous_namespace{file} , where file will be replaced with the base # name of the file that contains the anonymous namespace. By default # anonymous namespace are hidden. EXTRACT_ANON_NSPACES = YES # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all # undocumented members of documented classes, files or namespaces. # If set to NO (the default) these members will be included in the # various overviews, but no documentation section is generated. # This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_MEMBERS = NO # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all # undocumented classes that are normally visible in the class hierarchy. # If set to NO (the default) these classes will be included in the various # overviews. This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_CLASSES = NO # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all # friend (class|struct|union) declarations. # If set to NO (the default) these declarations will be included in the # documentation. HIDE_FRIEND_COMPOUNDS = NO # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any # documentation blocks found inside the body of a function. # If set to NO (the default) these blocks will be appended to the # function s detailed documentation block. HIDE_IN_BODY_DOCS = NO # The INTERNAL_DOCS tag determines if documentation # that is typed after a \internal command is included. If the tag is set # to NO (the default) then the documentation will be excluded. # Set it to YES to include the internal documentation. INTERNAL_DOCS = YES # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate # file names in lower-case letters. If set to YES upper-case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows # and Mac users are advised to set this option to NO. CASE_SENSE_NAMES = NO # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen # will show members with their full class and namespace scopes in the # documentation. If set to YES the scope will be hidden. HIDE_SCOPE_NAMES = NO # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen # will put a list of the files that are included by a file in the documentation # of that file. SHOW_INCLUDE_FILES = YES # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] # is inserted in the documentation for inline members. INLINE_INFO = YES # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen # will sort the (detailed) documentation of file and class members # alphabetically by member name. If set to NO the members will appear in # declaration order. SORT_MEMBER_DOCS = NO # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the # brief documentation of file, namespace and class members alphabetically # by member name. If set to NO (the default) the members will appear in # declaration order. SORT_BRIEF_DOCS = YES # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the # hierarchy of group names into alphabetical order. If set to NO (the default) # the group names will appear in their defined order. SORT_GROUP_NAMES = YES # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be # sorted by fully-qualified names, including namespaces. If set to # NO (the default), the class list will be sorted only by class name, # not including the namespace part. # Note This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # Note This option applies only to the class list, not to the # alphabetical list. SORT_BY_SCOPE_NAME = YES # The GENERATE_TODOLIST tag can be used to enable (YES) or # disable (NO) the todo list. This list is created by putting \todo # commands in the documentation. GENERATE_TODOLIST = YES # The GENERATE_TESTLIST tag can be used to enable (YES) or # disable (NO) the test list. This list is created by putting \test # commands in the documentation. GENERATE_TESTLIST = YES # The GENERATE_BUGLIST tag can be used to enable (YES) or # disable (NO) the bug list. This list is created by putting \bug # commands in the documentation. GENERATE_BUGLIST = YES # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or # disable (NO) the deprecated list. This list is created by putting # \deprecated commands in the documentation. GENERATE_DEPRECATEDLIST= YES # The ENABLED_SECTIONS tag can be used to enable conditional # documentation sections, marked by \if sectionname ... \endif. ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines # the initial value of a variable or define consists of for it to appear in # the documentation. If the initializer consists of more lines than specified # here it will be hidden. Use a value of 0 to hide initializers completely. # The appearance of the initializer of individual variables and defines in the # documentation can be controlled using \showinitializer or \hideinitializer # command in the documentation regardless of this setting. MAX_INITIALIZER_LINES = 50 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated # at the bottom of the documentation of classes and structs. If set to YES the # list will mention the files that were used to generate the documentation. SHOW_USED_FILES = YES # If the sources in your project are distributed over multiple directories # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy # in the documentation. The default is NO. SHOW_DIRECTORIES = NO # Set the SHOW_FILES tag to NO to disable the generation of the Files page. # This will remove the Files entry from the Quick Index and from the # Folder Tree View (if specified). The default is YES. SHOW_FILES = YES # Set the SHOW_NAMESPACES tag to NO to disable the generation of the # Namespaces page. This will remove the Namespaces entry from the Quick Index # and from the Folder Tree View (if specified). The default is YES. SHOW_NAMESPACES = YES # The FILE_VERSION_FILTER tag can be used to specify a program or script that # doxygen should invoke to get the current version for each file (typically from # the version control system). Doxygen will invoke the program by executing (via # popen()) the command command input-file , where command is the value of # the FILE_VERSION_FILTER tag, and input-file is the name of an input file # provided by doxygen. Whatever the program writes to standard output # is used as the file version. See the manual for examples. FILE_VERSION_FILTER = # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by # doxygen. The layout file controls the global structure of the generated output files # in an output format independent way. The create the layout file that represents # doxygen s defaults, run doxygen with the -l option. You can optionally specify a # file name after the option, if omitted DoxygenLayout.xml will be used as the name # of the layout file. LAYOUT_FILE = #---------------------------------------------------------------------------# configuration options related to warning and progress messages#--------------------------------------------------------------------------- # The QUIET tag can be used to turn on/off the messages that are generated # by doxygen. Possible values are YES and NO. If left blank NO is used. QUIET = NO # The WARNINGS tag can be used to turn on/off the warning messages that are # generated by doxygen. Possible values are YES and NO. If left blank # NO is used. WARNINGS = YES # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings # for undocumented members. If EXTRACT_ALL is set to YES then this flag will # automatically be disabled. WARN_IF_UNDOCUMENTED = YES # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for # potential errors in the documentation, such as not documenting some # parameters in a documented function, or documenting parameters that # don t exist or using markup commands wrongly. WARN_IF_DOC_ERROR = YES # This WARN_NO_PARAMDOC option can be abled to get warnings for # functions that are documented, but have no documentation for their parameters # or return value. If set to NO (the default) doxygen will only warn about # wrong or incomplete parameter documentation, but not about the absence of # documentation. WARN_NO_PARAMDOC = YES # The WARN_FORMAT tag determines the format of the warning messages that # doxygen can produce. The string should contain the $file, $line, and $text # tags, which will be replaced by the file and line number from which the # warning originated and the warning text. Optionally the format may contain # $version, which will be replaced by the version of the file (if it could # be obtained via FILE_VERSION_FILTER) WARN_FORMAT = "!!$file($line) $text" # The WARN_LOGFILE tag can be used to specify a file to which warning # and error messages should be written. If left blank the output is written # to stderr. WARN_LOGFILE = DoxygenLog.txt #---------------------------------------------------------------------------# configuration options related to the input files#--------------------------------------------------------------------------- # The INPUT tag can be used to specify the files and/or directories that contain # documented source files. You may enter file names like "myfile.cpp" or # directories like "/usr/src/myproject". Separate the files or directories # with spaces. INPUT = . # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is # also the default input encoding. Doxygen uses libiconv (or the iconv built # into libc) for the transcoding. See http //www.gnu.org/software/libiconv for # the list of possible encodings. INPUT_ENCODING = shift_jis # If the value of the INPUT tag contains directories, you can use the # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp # and *.h) to filter out the source-files in the directories. If left # blank the following patterns are tested # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 FILE_PATTERNS = # The RECURSIVE tag can be used to turn specify whether or not subdirectories # should be searched for input files as well. Possible values are YES and NO. # If left blank NO is used. RECURSIVE = YES # The EXCLUDE tag can be used to specify files and/or directories that should # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. EXCLUDE = # The EXCLUDE_SYMLINKS tag can be used select whether or not files or # directories that are symbolic links (a Unix filesystem feature) are excluded # from the input. EXCLUDE_SYMLINKS = NO # If the value of the INPUT tag contains directories, you can use the # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # certain files from those directories. Note that the wildcards are matched # against the file with absolute path, so to exclude all test directories # for example use the pattern */test/* EXCLUDE_PATTERNS = # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the # output. The symbol name can be a fully qualified name, a word, or if the # wildcard * is used, a substring. Examples ANamespace, AClass, # AClass ANamespace, ANamespace *Test EXCLUDE_SYMBOLS = # The EXAMPLE_PATH tag can be used to specify one or more files or # directories that contain example code fragments that are included (see # the \include command). EXAMPLE_PATH = # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp # and *.h) to filter out the source-files in the directories. If left # blank all files are included. EXAMPLE_PATTERNS = # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be # searched for input files to be used with the \include or \dontinclude # commands irrespective of the value of the RECURSIVE tag. # Possible values are YES and NO. If left blank NO is used. EXAMPLE_RECURSIVE = NO # The IMAGE_PATH tag can be used to specify one or more files or # directories that contain image that are included in the documentation (see # the \image command). IMAGE_PATH = # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program # by executing (via popen()) the command filter input-file , where filter # is the value of the INPUT_FILTER tag, and input-file is the name of an # input file. Doxygen will then use the output that the filter program writes # to standard output. If FILTER_PATTERNS is specified, this tag will be # ignored. INPUT_FILTER = # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern # basis. Doxygen will compare the file name with each pattern and apply the # filter if there is a match. The filters are a list of the form # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER # is applied to all files. FILTER_PATTERNS = # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using # INPUT_FILTER) will be used to filter the input files when producing source # files to browse (i.e. when SOURCE_BROWSER is set to YES). FILTER_SOURCE_FILES = NO #---------------------------------------------------------------------------# configuration options related to source browsing#--------------------------------------------------------------------------- # If the SOURCE_BROWSER tag is set to YES then a list of source files will # be generated. Documented entities will be cross-referenced with these sources. # Note To get rid of all source code in the generated output, make sure also # VERBATIM_HEADERS is set to NO. SOURCE_BROWSER = YES # Setting the INLINE_SOURCES tag to YES will include the body # of functions and classes directly in the documentation. INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct # doxygen to hide any special comment blocks from generated source code # fragments. Normal C and C++ comments will always remain visible. STRIP_CODE_COMMENTS = YES # If the REFERENCED_BY_RELATION tag is set to YES # then for each documented function all documented # functions referencing it will be listed. REFERENCED_BY_RELATION = NO # If the REFERENCES_RELATION tag is set to YES # then for each documented function all documented entities # called/used by that function will be listed. REFERENCES_RELATION = NO # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will # link to the source code. Otherwise they will link to the documentation. REFERENCES_LINK_SOURCE = YES # If the USE_HTAGS tag is set to YES then the references to source code # will point to the HTML generated by the htags(1) tool instead of doxygen # built-in source browser. The htags tool is part of GNU s global source # tagging system (see http //www.gnu.org/software/global/global.html). You # will need version 4.8.6 or higher. USE_HTAGS = NO # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen # will generate a verbatim copy of the header file for each class for # which an include is specified. Set to NO to disable this. VERBATIM_HEADERS = YES #---------------------------------------------------------------------------# configuration options related to the alphabetical class index#--------------------------------------------------------------------------- # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index # of all compounds will be generated. Enable this if the project # contains a lot of classes, structs, unions or interfaces. ALPHABETICAL_INDEX = NO # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns # in which this list will be split (can be a number in the range [1..20]) COLS_IN_ALPHA_INDEX = 5 # In case all classes in a project start with a common prefix, all # classes will be put under the same header in the alphabetical index. # The IGNORE_PREFIX tag can be used to specify one or more prefixes that # should be ignored while generating the index headers. IGNORE_PREFIX = #---------------------------------------------------------------------------# configuration options related to the HTML output#--------------------------------------------------------------------------- # If the GENERATE_HTML tag is set to YES (the default) Doxygen will # generate HTML output. GENERATE_HTML = YES # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `html will be used as the default path. HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for # each generated HTML page (for example .htm,.php,.asp). If it is left blank # doxygen will generate files with .html extension. HTML_FILE_EXTENSION = .html # The HTML_HEADER tag can be used to specify a personal HTML header for # each generated HTML page. If it is left blank doxygen will generate a # standard header. HTML_HEADER = # The HTML_FOOTER tag can be used to specify a personal HTML footer for # each generated HTML page. If it is left blank doxygen will generate a # standard footer. HTML_FOOTER = docs/hooter.html # The HTML_STYLESHEET tag can be used to specify a user-defined cascading # style sheet that is used by each HTML page. It can be used to # fine-tune the look of the HTML output. If the tag is left blank doxygen # will generate a default style sheet. Note that doxygen will try to copy # the style sheet file to the HTML output directory, so don t put your own # stylesheet in the HTML output directory as well, or it will be erased! HTML_STYLESHEET = docs/doxygen.css # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, # files or namespaces will be aligned in HTML using tables. If set to # NO a bullet list will be used. HTML_ALIGN_MEMBERS = YES # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the # page has loaded. For this to work a browser that supports # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). HTML_DYNAMIC_SECTIONS = NO # If the GENERATE_DOCSET tag is set to YES, additional index files # will be generated that can be used as input for Apple s Xcode 3 # integrated development environment, introduced with OSX 10.5 (Leopard). # To create a documentation set, doxygen will generate a Makefile in the # HTML output directory. Running make will produce the docset in that # directory and running "make install" will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find # it at startup. # See http //developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. GENERATE_DOCSET = NO # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the # feed. A documentation feed provides an umbrella under which multiple # documentation sets from a single provider (such as a company or product suite) # can be grouped. DOCSET_FEEDNAME = # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that # should uniquely identify the documentation set bundle. This should be a # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen # will append .docset to the name. DOCSET_BUNDLE_ID = # If the GENERATE_HTMLHELP tag is set to YES, additional index files # will be generated that can be used as input for tools like the # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) # of the generated HTML documentation. GENERATE_HTMLHELP = NO # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can # be used to specify the file name of the resulting .chm file. You # can add a path in front of the file if the result should not be # written to the html output directory. CHM_FILE = # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can # be used to specify the location (absolute path including file name) of # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run # the HTML help compiler on the generated index.hhp. HHC_LOCATION = # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag # controls if a separate .chi index file is generated (YES) or that # it should be included in the master .chm file (NO). GENERATE_CHI = NO # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING # is used to encode HtmlHelp index (hhk), content (hhc) and project file # content. CHM_INDEX_ENCODING = # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag # controls whether a binary table of contents is generated (YES) or a # normal table of contents (NO) in the .chm file. BINARY_TOC = NO # The TOC_EXPAND flag can be set to YES to add extra items for group members # to the contents of the HTML help documentation and to the tree view. TOC_EXPAND = NO # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER # are set, an additional index file will be generated that can be used as input for # Qt s qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated # HTML documentation. GENERATE_QHP = NO # If the QHG_LOCATION tag is specified, the QCH_FILE tag can # be used to specify the file name of the resulting .qch file. # The path specified is relative to the HTML output folder. QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating # Qt Help Project output. For more information please see # http //doc.trolltech.com/qthelpproject.html#namespace QHP_NAMESPACE = # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating # Qt Help Project output. For more information please see # http //doc.trolltech.com/qthelpproject.html#virtual-folders QHP_VIRTUAL_FOLDER = # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. # For more information please see # http //doc.trolltech.com/qthelpproject.html#custom-filters QHP_CUST_FILTER_NAME = # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see # a href="http //doc.trolltech.com/qthelpproject.html#custom-filters" Qt Help Project / Custom Filters /a . QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project s # filter section matches. # a href="http //doc.trolltech.com/qthelpproject.html#filter-attributes" Qt Help Project / Filter Attributes /a . QHP_SECT_FILTER_ATTRS = # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can # be used to specify the location of Qt s qhelpgenerator. # If non-empty doxygen will try to run qhelpgenerator on the generated # .qhp file. QHG_LOCATION = # The DISABLE_INDEX tag can be used to turn on/off the condensed index at # top of each HTML page. The value NO (the default) enables the index and # the value YES disables it. DISABLE_INDEX = NO # This tag can be used to set the number of enum values (range [1..20]) # that doxygen will group on one line in the generated HTML documentation. ENUM_VALUES_PER_LINE = 4 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. # If the tag value is set to FRAME, a side panel will be generated # containing a tree-like index structure (just like the one that # is generated for HTML Help). For this to work a browser that supports # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are # probably better off using the HTML help feature. Other possible values # for this tag are HIERARCHIES, which will generate the Groups, Directories, # and Class Hierarchy pages using a tree view instead of an ordered list; # ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which # disables this behavior completely. For backwards compatibility with previous # releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE # respectively. GENERATE_TREEVIEW = NONE # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be # used to set the initial width (in pixels) of the frame in which the tree # is shown. TREEVIEW_WIDTH = 6 # Use this tag to change the font size of Latex formulas included # as images in the HTML documentation. The default is 10. Note that # when you change the font size after a successful doxygen run you need # to manually remove any form_*.png images from the HTML output directory # to force them to be regenerated. FORMULA_FONTSIZE = 10 #---------------------------------------------------------------------------# configuration options related to the LaTeX output#--------------------------------------------------------------------------- # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will # generate Latex output. GENERATE_LATEX = NO # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `latex will be used as the default path. LATEX_OUTPUT = # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be # invoked. If left blank `latex will be used as the default command name. LATEX_CMD_NAME = # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to # generate index for LaTeX. If left blank `makeindex will be used as the # default command name. MAKEINDEX_CMD_NAME = # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact # LaTeX documents. This may be useful for small projects and may help to # save some trees in general. COMPACT_LATEX = NO # The PAPER_TYPE tag can be used to set the paper type that is used # by the printer. Possible values are a4, a4wide, letter, legal and # executive. If left blank a4wide will be used. PAPER_TYPE = # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX # packages that should be included in the LaTeX output. EXTRA_PACKAGES = # The LATEX_HEADER tag can be used to specify a personal LaTeX header for # the generated latex document. The header should contain everything until # the first chapter. If it is left blank doxygen will generate a # standard header. Notice only use this tag if you know what you are doing! LATEX_HEADER = # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated # is prepared for conversion to pdf (using ps2pdf). The pdf file will # contain links (just like the HTML output) instead of page references # This makes the output suitable for online browsing using a pdf viewer. PDF_HYPERLINKS = NO # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of # plain latex in the generated Makefile. Set this option to YES to get a # higher quality PDF documentation. USE_PDFLATEX = NO # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. # command to the generated LaTeX files. This will instruct LaTeX to keep # running if errors occur, instead of asking the user for help. # This option is also used when generating formulas in HTML. LATEX_BATCHMODE = NO # If LATEX_HIDE_INDICES is set to YES then doxygen will not # include the index chapters (such as File Index, Compound Index, etc.) # in the output. LATEX_HIDE_INDICES = NO #---------------------------------------------------------------------------# configuration options related to the RTF output#--------------------------------------------------------------------------- # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output # The RTF output is optimized for Word 97 and may not look very pretty with # other RTF readers or editors. GENERATE_RTF = NO # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `rtf will be used as the default path. RTF_OUTPUT = # If the COMPACT_RTF tag is set to YES Doxygen generates more compact # RTF documents. This may be useful for small projects and may help to # save some trees in general. COMPACT_RTF = NO # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated # will contain hyperlink fields. The RTF file will # contain links (just like the HTML output) instead of page references. # This makes the output suitable for online browsing using WORD or other # programs which support those fields. # Note wordpad (write) and others do not support links. RTF_HYPERLINKS = NO # Load stylesheet definitions from file. Syntax is similar to doxygen s # config file, i.e. a series of assignments. You only have to provide # replacements, missing definitions are set to their default value. RTF_STYLESHEET_FILE = # Set optional variables used in the generation of an rtf document. # Syntax is similar to doxygen s config file. RTF_EXTENSIONS_FILE = #---------------------------------------------------------------------------# configuration options related to the man page output#--------------------------------------------------------------------------- # If the GENERATE_MAN tag is set to YES (the default) Doxygen will # generate man pages GENERATE_MAN = NO # The MAN_OUTPUT tag is used to specify where the man pages will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `man will be used as the default path. MAN_OUTPUT = # The MAN_EXTENSION tag determines the extension that is added to # the generated man pages (default is the subroutine s section .3) MAN_EXTENSION = # If the MAN_LINKS tag is set to YES and Doxygen generates man output, # then it will generate one additional man file for each entity # documented in the real man page(s). These additional files # only source the real man page, but without them the man command # would be unable to find the correct page. The default is NO. MAN_LINKS = NO #---------------------------------------------------------------------------# configuration options related to the XML output#--------------------------------------------------------------------------- # If the GENERATE_XML tag is set to YES Doxygen will # generate an XML file that captures the structure of # the code including all documentation. GENERATE_XML = NO # The XML_OUTPUT tag is used to specify where the XML pages will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `xml will be used as the default path. XML_OUTPUT = # The XML_SCHEMA tag can be used to specify an XML schema, # which can be used by a validating XML parser to check the # syntax of the XML files. XML_SCHEMA = # The XML_DTD tag can be used to specify an XML DTD, # which can be used by a validating XML parser to check the # syntax of the XML files. XML_DTD = # If the XML_PROGRAMLISTING tag is set to YES Doxygen will # dump the program listings (including syntax highlighting # and cross-referencing information) to the XML output. Note that # enabling this will significantly increase the size of the XML output. XML_PROGRAMLISTING = NO #---------------------------------------------------------------------------# configuration options for the AutoGen Definitions output#--------------------------------------------------------------------------- # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will # generate an AutoGen Definitions (see autogen.sf.net) file # that captures the structure of the code including all # documentation. Note that this feature is still experimental # and incomplete at the moment. GENERATE_AUTOGEN_DEF = YES #---------------------------------------------------------------------------# configuration options related to the Perl module output#--------------------------------------------------------------------------- # If the GENERATE_PERLMOD tag is set to YES Doxygen will # generate a Perl module file that captures the structure of # the code including all documentation. Note that this # feature is still experimental and incomplete at the # moment. GENERATE_PERLMOD = NO # If the PERLMOD_LATEX tag is set to YES Doxygen will generate # the necessary Makefile rules, Perl scripts and LaTeX code to be able # to generate PDF and DVI output from the Perl module output. PERLMOD_LATEX = NO # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be # nicely formatted so it can be parsed by a human reader. This is useful # if you want to understand what is going on. On the other hand, if this # tag is set to NO the size of the Perl module output will be much smaller # and Perl will parse it just the same. PERLMOD_PRETTY = NO # The names of the make variables in the generated doxyrules.make file # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. # This is useful so different doxyrules.make files included by the same # Makefile don t overwrite each other s variables. PERLMOD_MAKEVAR_PREFIX = #---------------------------------------------------------------------------# Configuration options related to the preprocessor #--------------------------------------------------------------------------- # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will # evaluate all C-preprocessor directives found in the sources and include # files. ENABLE_PREPROCESSING = YES # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro # names in the source code. If set to NO (the default) only conditional # compilation will be performed. Macro expansion can be done in a controlled # way by setting EXPAND_ONLY_PREDEF to YES. MACRO_EXPANSION = NO # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES # then the macro expansion is limited to the macros specified with the # PREDEFINED and EXPAND_AS_DEFINED tags. EXPAND_ONLY_PREDEF = NO # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files # in the INCLUDE_PATH (see below) will be search if a #include is found. SEARCH_INCLUDES = YES # The INCLUDE_PATH tag can be used to specify one or more directories that # contain include files that are not input files but should be processed by # the preprocessor. INCLUDE_PATH = # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard # patterns (like *.h and *.hpp) to filter out the header-files in the # directories. If left blank, the patterns specified with FILE_PATTERNS will # be used. INCLUDE_FILE_PATTERNS = # The PREDEFINED tag can be used to specify one or more macro names that # are defined before the preprocessor is started (similar to the -D option of # gcc). The argument of the tag is a list of macros of the form name # or name=definition (no spaces). If the definition and the = are # omitted =1 is assumed. To prevent a macro definition from being # undefined via #undef or recursively expanded use the = operator # instead of the = operator. PREDEFINED = # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then # this tag can be used to specify a list of macro names that should be expanded. # The macro definition that is found in the sources will be used. # Use the PREDEFINED tag if you want to use a different macro definition. EXPAND_AS_DEFINED = # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then # doxygen s preprocessor will remove all function-like macros that are alone # on a line, have an all uppercase name, and do not end with a semicolon. Such # function macros are typically used for boiler-plate code, and will confuse # the parser if not removed. SKIP_FUNCTION_MACROS = YES #---------------------------------------------------------------------------# Configuration additions related to external references #--------------------------------------------------------------------------- # The TAGFILES option can be used to specify one or more tagfiles. # Optionally an initial location of the external documentation # can be added for each tagfile. The format of a tag file without # this location is as follows # TAGFILES = file1 file2 ... # Adding location for the tag files is done as follows # TAGFILES = file1=loc1 "file2 = loc2" ... # where "loc1" and "loc2" can be relative or absolute paths or # URLs. If a location is present for each tag, the installdox tool # does not have to be run to correct the links. # Note that each tag file must have a unique name # (where the name does NOT include the path) # If a tag file is not located in the directory in which doxygen # is run, you must also specify the path to the tagfile here. TAGFILES = # When a file name is specified after GENERATE_TAGFILE, doxygen will create # a tag file that is based on the input files it reads. GENERATE_TAGFILE = # If the ALLEXTERNALS tag is set to YES all external classes will be listed # in the class index. If set to NO only the inherited external classes # will be listed. ALLEXTERNALS = NO # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed # in the modules index. If set to NO, only the current project s groups will # be listed. EXTERNAL_GROUPS = YES # The PERL_PATH should be the absolute path and name of the perl script # interpreter (i.e. the result of `which perl ). PERL_PATH = #---------------------------------------------------------------------------# Configuration options related to the dot tool #--------------------------------------------------------------------------- # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base # or super classes. Setting the tag to NO turns the diagrams off. Note that # this option is superseded by the HAVE_DOT option below. This is only a # fallback. It is recommended to install and use dot, since it yields more # powerful graphs. CLASS_DIAGRAMS = YES # You can define message sequence charts within doxygen comments using the \msc # command. Doxygen will then run the mscgen tool (see # http //www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the # documentation. The MSCGEN_PATH tag allows you to specify the directory where # the mscgen tool resides. If left empty the tool is assumed to be found in the # default search path. MSCGEN_PATH = # If set to YES, the inheritance and collaboration graphs will hide # inheritance and usage relations if the target is undocumented # or is not a class. HIDE_UNDOC_RELATIONS = YES # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is # available from the path. This tool is part of Graphviz, a graph visualization # toolkit from AT T and Lucent Bell Labs. The other options in this section # have no effect if this option is set to NO (the default) HAVE_DOT = YES # By default doxygen will write a font called FreeSans.ttf to the output # directory and reference it in all dot files that doxygen generates. This # font does not include all possible unicode characters however, so when you need # these (or just want a differently looking font) you can specify the font name # using DOT_FONTNAME. You need need to make sure dot is able to find the font, # which can be done by putting it in a standard location or by setting the # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory # containing the font. DOT_FONTNAME = Tahoma # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. # The default size is 10pt. DOT_FONTSIZE = 8 # By default doxygen will tell dot to use the output directory to look for the # FreeSans.ttf font (which doxygen will put there itself). If you specify a # different font using DOT_FONTNAME you can set the path where dot # can find it using this tag. DOT_FONTPATH = "E \Program Files\Graphviz2.22\etc\fonts\tahoma.ttf" # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen # will generate a graph for each documented class showing the direct and # indirect inheritance relations. Setting this tag to YES will force the # the CLASS_DIAGRAMS tag to NO. CLASS_GRAPH = YES # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen # will generate a graph for each documented class showing the direct and # indirect implementation dependencies (inheritance, containment, and # class references variables) of the class with other documented classes. COLLABORATION_GRAPH = YES # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen # will generate a graph for groups, showing the direct groups dependencies GROUP_GRAPHS = YES # If the UML_LOOK tag is set to YES doxygen will generate inheritance and # collaboration diagrams in a style similar to the OMG s Unified Modeling # Language. UML_LOOK = YES # If set to YES, the inheritance and collaboration graphs will show the # relations between templates and their instances. TEMPLATE_RELATIONS = NO # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT # tags are set to YES then doxygen will generate a graph for each documented # file showing the direct and indirect include dependencies of the file with # other documented files. INCLUDE_GRAPH = YES # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and # HAVE_DOT tags are set to YES then doxygen will generate a graph for each # documented header file showing the documented files that directly or # indirectly include this file. INCLUDED_BY_GRAPH = YES # If the CALL_GRAPH and HAVE_DOT options are set to YES then # doxygen will generate a call dependency graph for every global function # or class method. Note that enabling this option will significantly increase # the time of a run. So in most cases it will be better to enable call graphs # for selected functions only using the \callgraph command. CALL_GRAPH = YES # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then # doxygen will generate a caller dependency graph for every global function # or class method. Note that enabling this option will significantly increase # the time of a run. So in most cases it will be better to enable caller # graphs for selected functions only using the \callergraph command. CALLER_GRAPH = YES # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen # will graphical hierarchy of all classes instead of a textual one. GRAPHICAL_HIERARCHY = YES # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES # then doxygen will show the dependencies a directory has on other directories # in a graphical way. The dependency relations are determined by the #include # relations between the files in the directories. DIRECTORY_GRAPH = YES # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images # generated by dot. Possible values are png, jpg, or gif # If left blank png will be used. DOT_IMAGE_FORMAT = png # The tag DOT_PATH can be used to specify the path where the dot tool can be # found. If left blank, it is assumed the dot tool can be found in the path. DOT_PATH = "../../../../Program Files/Graphviz2.22/bin" # The DOTFILE_DIRS tag can be used to specify one or more directories that # contain dot files that are included in the documentation (see the # \dotfile command). DOTFILE_DIRS = # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of # nodes that will be shown in the graph. If the number of nodes in a graph # becomes larger than this value, doxygen will truncate the graph, which is # visualized by representing a node as a red box. Note that doxygen if the # number of direct children of the root node in a graph is already larger than # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. DOT_GRAPH_MAX_NODES = 30 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the # graphs generated by dot. A depth value of 3 means that only nodes reachable # from the root by following a path via at most 3 edges will be shown. Nodes # that lay further from the root node will be omitted. Note that setting this # option to 1 or 2 may greatly reduce the computation time needed for large # code bases. Also note that the size of a graph can be further restricted by # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. MAX_DOT_GRAPH_DEPTH = 5 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent # background. This is disabled by default, because dot on Windows does not # seem to support this out of the box. Warning Depending on the platform used, # enabling this option may lead to badly anti-aliased labels on the edges of # a graph (i.e. they become hard to read). DOT_TRANSPARENT = YES # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output # files in one run (i.e. multiple -o and -T options on the command line). This # makes dot run faster, but since only newer versions of dot ( 1.8.10) # support this, this feature is disabled by default. DOT_MULTI_TARGETS = YES # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will # generate a legend page explaining the meaning of the various boxes and # arrows in the dot generated graphs. GENERATE_LEGEND = YES # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will # remove the intermediate dot files that are used to generate # the various graphs. DOT_CLEANUP = YES #---------------------------------------------------------------------------# Options related to the search engine#--------------------------------------------------------------------------- # The SEARCHENGINE tag specifies whether or not a search engine should be # used. If set to NO the values of all tags below this one will be ignored. SEARCHENGINE = YES